MIS 44048 F05 Steinberg_Weinroth

This course has two objectives:

Professionalism is expected throughout in comportment and outcome.

Students will be assigned to a project team. Each team works on a specific project throughout the semester. Class time will be available for team work rather than for conventional lecture and discussion. Each team will meet with

There are no regular class meetings on Tuesday except as announced by Dr. Weinroth for the day section.
> <br> The emphasis of this course is on writing and communication. This is not a class in which you will be taught new technologies by lecture. The emphasis is not on technologies used to accomplish information system development. As you design your system and develop your prototype you should use technologies that you are already familiar with. The instructor will help with use of technology (programming, database, etc.) as appropriate.
> <br> Each student takes on the roles of analyst and developer. Roles will change as the project demands.
> <br> The project is comprised of six phases. You work individually on the first phase and as a team on the remaining five phases. Refer to the material online for instruction and guidance about the phases.

A	>=90
B	80-89
C	70-79
D	60-69
E	<60

> Grades are not rounded and not curved. No exceptions. No incompletes will be granted because this is a group effort and if you do not do your part the whole team suffers. <br>
> Your grade is composed of individual and group contributions. See the schedule on Orion for details. <br>
> Note: For &quot;individual&quot; parts you get a grade for your work alone. Click <a href="http:/131.123.8.32/orion/src/sd1/762/!individual.htm">here for details. For "group" parts everyone your team gets the same grade.

This is a writing-intensive course and you are expected to do a substantial piece of writing. You will be given opportunities to submit your work for a pre-critique and revise and resubmit your work if you wish. Diagrams (graphs, flow-charts, ERDs, etc.), images, videos, music, stationary, logos and so on are important and undoubtedly necessary to the success of your project, but they are not writing. You can, however, accompany these items with a significant amount of interpretive commentary.

Each team will provide a member of the Technical Infrastructure Committee. This group will meet as needed to define the server infrastructure that all prototypes will be implemented on. All teams will use the same infrastructure meaning the same: operating system, database manager, programming language, etc.
> <br> The team will meet as needed and report to Dr. Steinberg when requested.

Textbook: None. You have taken the needed courses already. Here you put it all together. Supplement what you need with any other references (management, techinical, etc.) that you need.
> <br> Lateness: Not allowed. No exceptions. Lateness as a professional is not acceptable and it is not acceptable in this class either.
> <br> Attendance: Expected. The standard KSU allowances for absence are permitted with proper documentation. Any other absence will impact on your individual contribution score.
> <br> Computer virus: It is not nice to send a virus to a server. If you do then you may render all group projects useless. So be careful!
> <br> Students with Disability: In accordance with University policy, if you have a documented disability and require accomodations to obtain equal access in this course, please contact the instructor at the beginning of the semester or when given an assignment for which accomodation is required. Students with disabilities must verify their eligibility through the Office of Student Disability Services (SDS) in the Michael Schwartz Services Center (672-2972).
> <br> Backup Your Work: Expected. Your team will be provided space on a server. The server is not backed up. It is your responsibility to maintain backup copies of everything that you develop.